Description

Supports running cloud gov tests in CI.

Follow-up PR with a gov migration and acceptance test: #2291

Solution discussion

Uses a fully configured provider when using cloud-gov, why?

1. Enables running gov tests in the same process as cloud-dev/cloud-qa tests
2. Keeps the CI simple with a single acceptance-tests job and we can run the tests often

Alternatives considered:

1. Modify env-vars for each cloud-gov test run (similar to t.Setenv("MONGODB_ATLAS_LAST_VERSION", "1.2.3") but with MONGODB_ATLAS_PRIVATE/PUBLIC_KEY/BASE_URL++

• Does not allow running tests in parallel since env-vars would impact the "normal" acceptance tests

2. Run a separate process/workflow

• Would require different CI workflows, but config would be a bit shorter as the provider would read env-vars directly

Link to any related issue(s): CLOUDP-250271

Type of change:

• Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
• New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
• Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contributing guides
• I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code
• If changes include deprecations or removals, I defined an isolated PR with a relevant title as it will be used in the auto-generated changelog.
• If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments